Managing User Stories

Assuming that the system documentation produced by the Extreme Programming (XP) process is the actual code, we propose to enrich this documentation by aggregating the user stories (system requirements) to the final product, the code. In XP system requirements are elicited from clients using a template named user story cards that are further discarded. By simply annexing the user stories as they are to the correspondent piece of code they relate to, we would already have the following gains: We go beyond annexing the user stories to code and propose a new organization to the information that is already elicited through the user stories. We base our proposal in our past experience developing software using scenarios. We are providing a scenario structure in which to capture and record the use stories that will provide